Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1209

reference
536-tree-1
name
1209
tree-preservation-order

undefined

536-tpo-1
uprn
address-text
point
POINT (-1.022893 50.884708)
geometry
MULTIPOLYGON (((-1.022850 50.884703,-1.022852 50.884712,-1.022858 50.884719,-1.022868 50.884725,-1.022879 50.884729,-1.022893 50.884731,-1.022918 50.884726,-1.022927 50.884720,-1.022933 50.884712,-1.022936 50.884704,-1.022934 50.884696,-1.022928 50.884688,-1.022919 50.884682,-1.022907 50.884678,-1.022894 50.884677,-1.022880 50.884678,-1.022868 50.884682,-1.022859 50.884688,-1.022853 50.884695,-1.022850 50.884703)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL